Application development involving instant protoyping

ABSTRACT

A system for developing software provides a graphical user interface on a display of a client device, the graphical user interface displaying features from a library of features for a custom software application, implements simulations of a plurality of the features available for demonstration through the graphical user interface, stores blocks of source code for each feature in a source code repository wherein the blocks are adapted to provide an actual application when compiled by developers, receives from the client device, by a server running a software building component, one or more selected features for the software application, automatically integrates, by the software building component, the one or more selected features to generate an integrated feature set based on attributes of each of the selected features and an inter-feature rules set, and generates an interactive visualization of a navigable prototype of the software application based on the integrated feature set.

CROSS REFERENCE TO RELATED APPLICATIONS

This is a continuation-in-part of U.S. patent application Ser. No. 17/348,695, filed Jun. 15, 2021, which claims priority to U.S. Provisional Patent Application Ser. No. 63/039,968, filed Jun. 16, 2020, and is a continuation-in-part of U.S. application Ser. No. 16/854,805, filed Apr. 21, 2020, now U.S. Pat. No. 11,086,599, which is a continuation of U.S. application Ser. No. 15/786,431, filed Oct. 17, 2017, now U.S. Pat. No. 10,649,741, which claims the benefit of U.S. Provisional Patent Application No. 62/408,935, filed on Oct. 17, 2016, and a continuation-in-part of U.S. patent application Ser. No. 17/120,118, filed Dec. 12, 2020, which claims the benefit of 62/948,100, filed Dec. 13, 2019, and is a continuation-in-part of U.S. patent application Ser. No. 16/854,805, filed Apr. 21, 2020, now U.S. Pat. No. 11,086,599, which is a continuation of U.S. application Ser. No. 15/786,431, filed Oct. 17, 2017, now U.S. Pat. No. 10,649,741, which claims the benefit of U.S. Provisional Patent Application No. 62/408,935, filed on Oct. 17, 2016, the entirety of each of which are herein incorporated by reference.

FIELD OF THE INVENTION

Embodiments of the present invention related to the field of software development. Specifically, embodiments of the present invention are related to systems and methods for developing software involving instant prototyping.

BACKGROUND

The process of working with vendors to develop desired software from initial idea through final software involves many stages and can take many months or years from start to finish. This process can oftentimes result in projects dying because of the complexity and the extended time from the initial excitement of the new idea to receiving anything tangible while also paying for potentially increasing development costs. Techniques for improving this process, which can improve the design process and provide greater efficiencies for vendors, are desired.

As generally understood, the conventional approach for developing a custom software application is to engage designers to develop the interface designs, the visual component, and software developers to implement the customer requirements for the software application including the design aspect into working source and object code (e.g., adapted for selected operating systems). The interactions with the software developer may involve initial conversations, artwork, or input from designers (that develop the user interface layout). The three party interaction can result in deficiencies in efficiency, pricing, and consistency.

Overall, there can be one or more technical problems related to software development, and the integration of source code development and user interface design for software applications.

SUMMARY OF THE INVENTION

According to embodiments of the present invention, a system for creating software is disclosed. The system includes at least one processor; and at least one memory operatively coupled to the at least one processor, the at least one processor configured to acquire computer readable instructions stored in the at least one memory and execute the instructions including instructions to cause the system to provide a graphical user interface on a display of a client device, the graphical user interface displaying a plurality of features from a library of user-selectable features for a custom software application and implement simulations of a plurality of the features available for demonstration through the graphical user interface; store blocks of source code for each feature in a source code repository, wherein the blocks are adapted to provide an actual application when compiled by developers; receive from the client device, by a server running a software building component of a software development application, one or more selected features for the software application; automatically integrate, by the software building component, the one or more selected features to generate an integrated feature set based on attributes of each of the selected features and an inter-feature rules set, and generate on the graphical user interface an interactive visualization of a navigable prototype of the software application based on the integrated feature set.

In some embodiments, the rules set define relationships or associations between features of the library of features. In some of these embodiments, the instructions to cause the system to automatically integrate the one or more selected features further include instructions to cause the system to determine for each feature of the selected features one or more related features based on the rules set, and determine the type of interaction between the selected features based on the attributes of each feature. In some of these embodiments, the instructions further include instructions to cause the system to automatically identify and add a new feature from the library of features to the selected features based on the rules set.

In certain embodiments, the attributes of a feature include a first set of attributes configured to regulate how the feature may be called, and a second set of attributes configured to regulate which features the feature may call. In some of these embodiments, the feature includes an interactive region configured to host an interactive element, the interactive element being configured to link to another feature and call that feature when the interactive element is actuated.

In some embodiments, the instructions further include instructions to cause the system to generate a screen flow view of the integrated features set, the screen flow view including the features of the integrated set interlinked by connectors that represent the relationships between the features. In some of these embodiments, both the features of the integrated set and the connectors between can be edited on the screen flow view.

In certain embodiments, the rules are updated based on a history of selection of features for the software application.

In some embodiments, the instructions further include instructions to cause the system to generate source code for the software application based on the integrated feature set and using the blocks of source code.

In certain embodiments, the instructions further include instructions to cause the system to provide the user with the opportunity to select a template from one or more templates, wherein each template includes a set of predetermined interconnected features, and subsequently provide the user via the graphical user interface the opportunity to select to add features to the template, and in response, the system is configured to automatically interconnect the selected added features with the set of predetermined interconnected features by using the set of rules, which provides an interactive prototype within the graphical user interface.

According to embodiments of the present invention, a computer-implemented method of a developing software is disclosed. The method includes providing a graphical user interface on a display of a client device, the graphical user interface displaying a plurality of features from a library of user-selectable features for a custom software application; implementing simulations of a plurality of the features available for demonstration through the graphical user interface; receiving from the client device, by a server running a software building component of a software development application, one or more selected features for the software application; automatically integrating, by the software building component, the one or more selected features to generate an integrated feature set based on attributes of each of the selected features and an inter-feature rules set, and generating on the graphical user interface an interactive visualization of a navigable prototype of the software application based on the integrated feature set.

In some embodiments, the rules set define relationships or associations between features of the library of features. In some of these embodiments, automatically integrating the one or more selected features includes determining for each feature of the selected features one or more related features based on the rules set, and determining the type of interaction between the selected features based on the attributes of each feature. In some of these embodiments, the method further includes automatically identifying and adding a new feature from the library of features to the selected features based on the rules set.

In certain embodiments, the attributes of a feature include a first set of attributes configured to regulate how the feature may be called, and a second set of attributes configured to regulate which features the feature may call. In some of these embodiments, the feature includes an interactive region configured to host an interactive element, the interactive element being configured to link to another feature and call that feature when the interactive element is actuated.

In some embodiments, the method further includes generating a screen flow view of the integrated features set, the screen flow view including the features of the integrated set interlinked by connectors that represent the relationships between the features. In some of these embodiments, both the features of the integrated set and the connectors between can be edited on the screen flow view.

In certain embodiments, the rules are updated based on a history of selection of features for the software application.

In some embodiments, the method further includes generating source code for the software application based on the integrated feature set.

In certain embodiments, the method further comprises providing the user with the opportunity to select a template from one or more templates, wherein each template comprises a set of predetermined interconnected features, and subsequently providing the user via the graphical user interface the opportunity to select to add features to the template, and in response, automatically interconnecting the selected added features with the set of predetermined interconnected features by using the set of rules, which provides an interactive prototype within the graphical user interface.

BRIEF DESCRIPTION OF THE DRAWINGS

Various features of examples and embodiments in accordance with the principles described herein may be more readily understood with reference to the following detailed description taken in conjunction with the accompanying drawings, where like reference numerals designate like structural elements, and in which:

FIG. 1 is a simplified block diagram of a distributed computer network according to an embodiment of the present invention.

FIG. 2 shows an exemplary computer system such as a client system according to an embodiment of the present invention.

FIG. 3 illustrates a flow chart of an interactive application building process according to an embodiment of the present invention.

FIG. 4 illustrates a system for developing software according to an embodiment of the present invention.

FIG. 5A illustrates an exemplary graphical user interface according to an embodiment of the present invention.

FIG. 5B illustrates graphical user interfaces displaying a library of templates, according to an embodiment of the present invention.

FIG. 6A illustrates a feature as a displayed screen of an application according to an embodiment of the present invention.

FIG. 6B illustrates a representation of a feature according to an embodiment of the present invention.

FIG. 7 illustrates two features as displayed screens, according to an embodiment of the present invention.

FIG. 8 illustrates an exemplary hierarchy of attributes for a feature that governs the feature's interaction with other features, according to an embodiment of the present invention.

FIG. 9 illustrates a screen flow view of an integrated build card according to an embodiment of the present invention.

FIG. 10 illustrates a screenshot of a prototype of the software application according to an embodiment of the present invention.

FIG. 11 illustrates a visual representation of a graph database according to an embodiment of the present invention.

FIG. 12 illustrates a visual representation of different nodes types in the graph database according to an embodiment of the present invention.

FIG. 13 is an illustrative functional block diagram of knowledge graph based recommendation tool according to an embodiment of the present invention.

FIG. 14 illustrates a visual representation of a new build card and relation to graph database for illustrative recommendation tool according to an embodiment of the present invention.

FIG. 15 is a functional block diagram for producing, updating, and making the graph database live in the system according to an embodiment of the present invention.

FIG. 16 is a functional block diagram for a knowledge graph incorporating node embedding into the tool according to an embodiment of the present invention.

FIG. 17 is an illustrative method for providing node embedding according to an embodiment of the present invention.

FIG. 18 is an illustrative method for generating a score and recommending a feature according to an embodiment of the present invention.

FIG. 19 is an illustrative method for automatically selecting connections to use between features included for a prototype according to an embodiment of the present invention.

Certain examples and embodiments have other features that are one of in addition to and in lieu of the features illustrated in the above-referenced figures. These and other features are detailed below with reference to the above-referenced figures.

DETAILED DESCRIPTION OF THE INVENTION

Embodiments of the present invention disclose a system and method that automate aspects of developing software applications. Specifically, embodiments of the present invention provide a process as part of a customer driven application development platform that includes a process stage that generates an early prototype of the customer's desired application for inspection and fine tuning by the customer. A computer-implemented process can be implemented that provides a platform that is accessible by a customer using conventional browsers. The platform can be a cloud service that permits the user to interact with the platform through graphical user interfaces to complete the different stages of the application development process. That would generally be understood to involve a combination of one or more computers, software implemented on the one or more computers that configures the computers to provide a specialized application, and online, Internet website access, to the functionality through a (conventional) browser or in some cases, a software application (e.g., a mobile app). The platform or system can be structured to define features as individual elements having certain characteristics such as meta data. The primary focus of this application is a subsystem directed to generating an instant prototype or quick delivery prototype. The sub-system may be part of a platform or system configured to generate code for a software application based on user selections of features and on the instant prototype. The customer can interact with the platform and by as little selecting a set of features, be able to receive a prototype. This is performed by providing a visual representation of the screen that will be displayed by the desired software based on the selected features. The prototype will be functional in that at the minimum there will be live areas in displayed screens (e.g., a representation of a mobile phone screen displayed through a web browser or other graphical user interface) that the customer can “click” or interact with that in response, will display a connected next screen. The platform can permit the user to edit the prototype or prototype demonstration by changing the flow of screen using interactive visual options such as through a displayed screen on a browser. A prototype engine can run the prototype by using meta data or structure stored for the features such as for a particular project to generate the visual display consistent with the feature. This process can for example generate the prototype, that generally simulates the expected user interactive experience, extremely quickly (immediately) in response to the user desired specification and software design such as by simply pressing a button to be able to see an early version of the desired software in operation. For example, simply by pressing a preview button, the user can be immediately cause the display of an operable interactive prototype displayed using screen or window representations. This can be at the initial process stage when a user uses the platform to specify the requirements (communicates the desired software application) and as such can also be given the ability to provide interactive feedback and design refinement with the platform interface on the proposed design requirement (including visual design) at this initial software development or engagement stage. It can be provided in other situations.

The platform is configured to automatically connect and arrange features (and corresponding screens) to provide the prototype. In some embodiments, this is performed by using underlying set of inter-feature characteristics information. This inter-feature information can be information that summarizes a history of user interaction involved in creating new software applications using features. The history may involve many different interactions including inter-screen connections. The user or customer can edit the arrangement. An advantage being that the timely and overwhelming task of handling the minutiae of selecting each feature, selecting what it connects to, and how it connects to is automatically performed. This can lead to the customer only need to conduct fine tuning. The use of historical information can provide the capability to automatically and dynamically update how features are interconnected as additional historical information are obtained, aggregated and processed for use. Overall, these are computer implemented techniques that provide a significant step forward compared to the known processes. In preferred embodiments, the platform is an online software development platform that is used by the public to engage a company to develop a particular software application for the customer. An example of such a system is illustratively described in U.S. Patent Publication No. 20180107459, by Dugal et al., filed Oct. 17, 2017, which is incorporated herein by reference in its entirety. The platform is preferably configured to provide the user, a potential customer, with the ability to interact with different interactive user interfaces to intuitively specify the requirements for the desired custom software application. The platform can be configured to operate as an application in object code that interacts with the user. The platform preferably includes a repository of existing source code for individual features that have been previously collected, used and/or tested to implement a corresponding feature. This source code can be reused, modified or compiled during the software development to produce the actual software application sought by the user. The platform preferably includes separate from the source code and object code for the features, object code adapted into the application of the platform (operating and existing in object code) that is configured to be a simulation of an actual corresponding feature (e.g., without the need to compile the code to create the simulation). This provides dynamic live features of the software development platform that are a component of the object code of that application. The platform maintains an association between the integrated object code simulation or interactive representation and the source code for the actual feature to be used in custom developed application. These are predetermined or preconfigured aspects of the platform. Thus, the system is configured to maintain different modes of a feature, including one that is an object code simulation and one that is the source code for the actual feature for use in developed application. The platform can also include a subsystem that communicates with a set of third party software developers to communicate the requirements (via messaging) and to engage the developers to develop additional source code or desired modification that after a query to the existing database of feature source code is determined to be needed or unavailable in the repository, thus requiring the developers to create new code for requirements or selections that are not in the repository (which is communicated via the platform). The platform can also communicate the requirements internally via electrical communications and in response automatically generate or assemble source code that contains the source code for the selected features from the repository. The repository can store different version of the source code such for different operating system or different end use platforms (e.g., mobile phones versus laptops). As part of the software development process, the platform can display interfaces that requires the user to select the operating system and end user platform. The platform takes that selection into account in pricing and/or generating or assembling source code for a customer's actual application.

In operation, in embodiments of the present invention, the features and described inter feature relationship are preconfigured when a user accesses the platform to select features and select to view the prototype (instantly).

The platform can be configured to allow the user to select the desired features as a preliminary step in order to specify the requirements for the desired custom software application. In response, the platform can use that information to automatically generate pricing taking into account selected features.

The platform can therefore be configured for the user to perform the design process or a portion thereof, e.g., on its own without the need to involve designers or third party user interface design applications, and to have a general initial (mutual) understanding of expectation and scope through this process. The platform can preferably provide the user with an integrated resource for design and the automatic generation of prototypes or simulations in addition with a streamlined process for software development where there is preexisting common structure between design and development such as by way of correspondence between prototype visualization and designed corresponding source code for the actual software that is part of the platform.

Preferably, the prototyping has limited functionality and is a simulation provided through the interface of the software development platform. For example, a feature to reset a password as a prototype is configured to display the relevant custom application screens, not actually require a true login credentials or to send an email resent link. It is focused on the in-software shell interaction.

The term prototype is used herein to refer to a simulation of a desired software application (based on user requirements) graphically provided within a user interface of an online platform by displaying simulated user interfaces within the environment of the graphical interface of an online platform that provides online software development tools such as a software application development platform. The simulation corresponds to a desired actual application. This is so as to clarify that the general usage of prototype can refer to an early or experimental version of an actual software application running as opposed to a simulation within the interface of the software development platform wherein the prototype process within the software development application is adapted to collect user requirements and specify design characteristics related to contents of interfaces, interaction, and flow of the desired actual application for that customer.

FIG. 1 is a simplified block diagram of a distributed computer network 100 incorporating an embodiment of the present invention. Computer network 100 includes a number of client systems 105, 110, and 115, and a server system 120 coupled to a communication network 125 via a plurality of communication links 130. Communication network 125 provides a mechanism for allowing the various components of distributed network 100 to communicate and exchange information with each other.

Communication network 125 may itself be comprised of many interconnected computer systems and communication links. Communication links 130 may be hardwire links, optical links, satellite or other wireless communications links, wave propagation links, or any other mechanisms for communication of information. Various communication protocols may be used to facilitate communication between the various systems shown in FIG. 1 . These communication protocols may include TCP/IP, HTTP protocols, wireless application protocol (WAP), vendor-specific protocols, customized protocols, and others. While in one embodiment, communication network 125 is the Internet, in other embodiments, communication network 125 may be any suitable communication network including a local area network (LAN), a wide area network (WAN), a wireless network, an intranet, a private network, a public network, a switched network, Internet telephony, IP telephony, digital voice, voice over broadband (VoBB), broadband telephony, Voice over IP (VoIP), public switched telephone network (PSTN), and combinations of these, and the like.

System 100 in FIG. 1 is merely illustrative of an embodiment and does not limit the scope of the systems and methods as recited in the claims. One of ordinary skill in the art would recognize other variations, modifications, and alternatives. For example, more than one server system 120 may be connected to communication network 125. As another example, a number of client systems 105, 110, and 115 may be coupled to communication network 125 via an access provider (not shown) or via some other server system. An instance of a server system 120 and a computing device 105 may be part of the same or a different hardware system. An instance of a server system 120 may be operated by a provider different from an organization operating an embodiment of a system for specifying an object in a design, or may be operated by the same organization operating an embodiment of a system for specifying an object in a design.

Client systems 105, 110, and 115 typically request information from a server system which provides the information. Server systems by definition typically have more computing and storage capacity than client systems. However, a particular computer system may act as both a client and a server depending on whether the computer system is requesting or providing information. Aspects of the system may be embodied using a client-server environment or a cloud-cloud computing environment.

Server 120 is responsible for receiving information requests from client systems 105, 110, and 115, performing processing required to satisfy the requests, and for forwarding the results corresponding to the requests back to the requesting client system. The processing required to satisfy the request may be performed by server system 120 or may alternatively be delegated to other servers connected to communication network 125.

Client systems 105, 110, and 115 enable users to access and query information or applications stored by server system 120. Some example client systems include portable electronic devices (e.g., mobile communication devices) such as the Apple iPhone®, the Apple, or any device running the Apple iOS™, Android™ OS, Google Chrome OS, Symbian OS®, or Windows Mobile® OS. In a specific embodiment, a “web browser” application executing on a client system enables users to select, access, retrieve, or query information and/or applications stored by server system 120. Examples of web browsers include the Android browser provided by Google, the Safari® browser provided by Apple, the Opera Web browser provided by Opera Software, and Internet Explorer Mobile browsers provided by Microsoft Corporation, the Firefox® and Firefox for Mobile browsers provided by Mozilla®, and others.

FIG. 2 shows an exemplary computer system such as a client system of the present invention. In an embodiment, a user interfaces with the system through a client system, such as shown in FIG. 2 . Mobile client communication or portable electronic device 200 includes a display, screen, or monitor 205, housing 210, and input device 215. Housing 210 houses familiar computer components, some of which are not shown, such as a processor 220, memory 225, battery 230, speaker, transceiver, antenna 235, microphone, ports, jacks, connectors, camera, input/output (I/O) controller, display adapter, network interface, mass storage devices 240, and the like. Computer system 200 may include a bus or other communication mechanism for communicating information between components. Mass storage devices 240 may store a user application and system software components. Memory 225 may store information and instructions to be executed by processor 220.

Input device 215 may also include a touchscreen (e.g., resistive, surface acoustic wave, capacitive sensing, infrared, optical imaging, dispersive signal, or acoustic pulse recognition), keyboard (e.g., electronic keyboard or physical keyboard), buttons, switches, stylus, gestural interface (contact or non-contact gestures), biometric input sensors, or combinations of these.

Mass storage devices 240 may include flash and other nonvolatile solid-state storage or solid-state drive (SSD), such as a flash drive, flash memory, or USB flash drive. Other examples of mass storage include mass disk drives, floppy disks, magnetic disks, optical disks, magneto-optical disks, fixed disks, hard disks, CD-ROMs, recordable CDs, DVDs, recordable DVDs (e.g., DVD-R, DVD+R, DVD-RW, DVD+RW, HD-DVD, or Blu-ray Disc), battery-backed-up volatile memory, tape storage, reader, and other similar media, and combinations of these.

System 100 may also be used with computer systems having different configurations, e.g., with additional or fewer subsystems. For example, a computer system could include more than one processor (i.e., a multiprocessor system, which may permit parallel processing of information) or a system may include a cache memory. The computer system shown in FIG. 2 is but an example of a computer system suitable for use. Other configurations of subsystems suitable for use will be readily apparent to one of ordinary skill in the art. For example, in a specific implementation, the computing device is mobile communication device such as a smartphone or tablet computer. Some specific examples of smartphones include the Droid Incredible and Google Nexus One®, provided by HTC Corporation, the iPhone® or iPad®, both provided by Apple, and many others. The computing device may be a laptop or a netbook. In another specific implementation, the computing device is a non-portable computing device such as a desktop computer or workstation.

A computer-implemented or computer-executable version of the program instructions useful to practice the present invention may be embodied using, stored on, or associated with computer-readable medium. A computer-readable medium may include any medium that participates in providing instructions to one or more processors for execution. Such a medium may take many forms including, but not limited to, nonvolatile, volatile, and transmission media. Nonvolatile media includes, for example, flash memory, or optical or magnetic disks. Volatile media includes static or dynamic memory, such as cache memory or RAM. Transmission media includes coaxial cables, copper wire, fiber optic lines, and wires arranged in a bus. Transmission media can also take the form of electromagnetic, radio frequency, acoustic, or light waves, such as those generated during radio wave and infrared data communications.

For example, a binary, machine-executable version, of the software useful to practice embodiments of the present invention may be stored or reside in RAM or cache memory, or on mass storage device 240. The source code of this software may also be stored or reside on mass storage device 240 (e.g., flash drive, hard disk, magnetic disk, tape, or CD-ROM). As a further example, code useful for practicing embodiments of the invention may be transmitted via wires, radio waves, or through a network such as the Internet. In another specific embodiment, a computer program product including a variety of software program code to implement features of embodiments of the invention is provided.

Computer software products may be written in any of various suitable programming languages, such as C, C++, C#, Pascal, Fortran, Perl, Matlab (from MathWorks, www.mathworks.com), SAS, SPSS, JavaScript, CoffeeScript, Objective-C, Objective-J, Ruby, Python, Erlang, Lisp, Scala, Clojure, and Java. The computer software product may be an independent application with data input and data display modules. Alternatively, the computer software products may be classes that may be instantiated as distributed objects. The computer software products may also be component software such as Java Beans (from Oracle) or Enterprise Java Beans (EJB from Oracle).

An operating system for the system may be the Android operating system, iPhone OS (i.e., iOS), Symbian, BlackBerry OS, Palm web OS, bada, MeeGo, Maemo, Limo, or Brew OS. Other examples of operating systems include one of the Microsoft Windows family of operating systems (e.g., Windows 95, 98, Me, Windows NT, Windows 2000, Windows XP, Windows XP x64 Edition, Windows Vista, Windows 7, Windows CE, Windows Mobile, Windows Phone 7), Linux, HP-UX, UNIX, Sun OS, Solaris, Mac OS X, Alpha OS, AIX, IRIX32, or IRIX64. Other operating systems may be used.

Furthermore, the computer may be connected to a network and may interface to other computers using this network. The network may be an intranet, internet, or the Internet, among others. The network may be a wired network (e.g., using copper), telephone network, packet network, an optical network (e.g., using optical fiber), or a wireless network, or any combination of these. For example, data and other information may be passed between the computer and components (or steps) of a system useful in practicing the invention using a wireless network employing a protocol such as Wi-Fi (IEEE standards 802.11, 802.11a, 802.11b, 802.11e, 802.11g, 802.11i, and 802.11n, just to name a few examples). For example, signals from a computer may be transferred, at least in part, wirelessly to components or other computers.

FIG. 3 illustrates a flow chart of an interactive application building process 300, according to an embodiment of the present invention. A user may interact from a browser or other application on their client device to participate in the process. The application development system of the present invention packages a set of selected features into a functional prototype of software application by setting up and regulating the flow of data between the features based on attributes embedded in each feature. The system implements a method that includes providing a graphical user interface on a display of a client device, the graphical user interface displaying a plurality of features from a library of features for a custom software application; receiving from the client device, by a server running a software building component, one or more selected features for the software application; automatically integrating, by the software building component, the one or more selected features to generate an integrated feature set based on attributes of each of the selected features and an inter-feature rules set, and generating on the graphical user interface an interactive visualization of a navigable prototype of the software application based on the integrated feature set. In some embodiments, the system further comprises customizing a feature by receiving from the client device one or more inputs for modifying attributes for the feature. The system may also further provide for customizing by enabling the addition, subtraction, editing, or reordering of features or the editing of connections between the features.

FIG. 4 illustrates a system for developing software according to an embodiment of the present invention. The system includes an application development software application 420 installed on an electronic device 410 and a builder software application 440 implemented on one or more servers 430. The electronic device 410 is preferably a desktop computer that can communicate with server via mobile networks or other wireless networks. Each of the electronic device and servers is a computer system that includes a microprocessor and volatile and non-volatile memory to configure the computer system. The computer system also includes a network connection interface that allows the computer system to communicate with another computer system over a network. Each software application may also be used independently or in conjunction with another software application to strengthen or supplement functionalities of the other software application.

The builder application 440 installed on the server 430 maintains a library of features for a software application. The library of features may be stored in a database 460. The builder application 440 is configured to transmit to the software development application on the client computer 410 the library of features, to receive a selection of a set of features, integrate the selected features into an integrated build card, and generate an interactive visualization of a prototype to the software on the client device. The builder application further maintains a rules database 470 configured to store and update rules governing interactions including connections between features of the library.

The software development application 420 is configured to provide a graphical user interface that enables a customer to select and customize a set of features as part of a build card for building an early prototype of the customer's desired application for inspection and fine tuning by the customer. In some embodiments, the software development application 420 is a web application provided by the builder application on the server and configured to run in a conventional browser. In a preferred embodiment, the software development application is the conventional browser 420 configured to access an application development website provided by the server.

Feature database 640 an also include source code for each of the plurality of available features. The saved source code provides a repository of source code for available features that the platform can use to generate object code for the actual application (e.g., based on the selected operating system) and/or to send the source code to select third party software developers to perform desired integration or modification based on customer specified requirements. The prototype engine 450 preferably uses object code and related data for corresponding features (e.g., without using or compiling the source code for actual implementation) to provide simulation of a set of specified requirement and the ability to interact to arrange or rearrange graphical elements or interface interactions. The simulated features may be based on the source code from the repository in database 640. Preferably, the live feature provides greater flexibility and efficiency.

FIG. 5A illustrates an exemplary graphical user interface 500 according to an embodiment of the present invention. The graphical user interface may be displayed in a web browser of a client computing device as part of a web page served by a server. The graphical user interface of embodiments of the present invention is configured to enable a user to select from a library of software features 510 to build a software application. The library of features 510 may be presented as a set of icons, a list, a drop down menu, or any other means of presenting information on graphical user interface.

A feature of the software application is a function or set of functions for the application. Conceptually, the feature is the atomic unit of the software project, according to embodiments of the present invention. That is, a feature is an independent unit of predefined functionality that comprises the basic building block of the software according to embodiments of the present invention. Accordingly, a feature is the smallest unit of the desired software application that the customer can employ (or need conceptualize). Further, a feature can be employed in disparate applications with minimal to no change to its core functionality, as will be described further down in this specification. This modular nature of the feature enables embodiments of the system of the present invention to build a prototype merely by logically connecting a selected set of features. In some embodiments, source code for the application or an intermediate representation thereof may be collected or assembled (and saved) based on the prototype. Embodiments of the present invention thus enable the user to select a set of features to be automatically assembled into a working prototype to serve as a basis for an application.

Functionally, a feature includes one or more screens that are logically linked and provide a particular function or set of functions for the application. For example, for a mobile application, a feature's interface may comprise a single screen or a set of logically linked screen, each of which may be invoked from another screen of the set. For a desktop application, a feature's interface may comprise a screen, a set of screens, a frame embedded in a screen provided by another feature, or combinations thereof. Each screen of the feature may exhibit one or more display regions and one or more interactive regions. The display regions serve to display content whereas the interactive region serve to interact with a user of the application, as will be described further in this specification. Metadata associated with each feature governs how each display region and region of the feature connects to other features of the library of feature. That is, a feature's metadata controls which others features it may call or be invoked by.

At the code level, a feature may represent one or more blocks of software code. For example, a feature may represent a set of objects and data configured to provide a particular function or set of functions to the software application. Thus, the one or more blocks of code may be compiled into one or more object files corresponding to the feature during the software build. The object files may be linked with other object files of other features during the software build according to the configuration of each feature to provide executable code for the application. In the alternative, the feature may correspond to one or more object files or a combination of blocks of source code and object files. For example, a feature at the code level may represent a combination of pre-processor directives, source code, object code/files, including form various libraries, standard and otherwise.

A feature may include a functionality that can be implemented in a modular fashion and that can be interchangeable between multiple software applications. For example, a feature that requires a user of software application to login (or a login feature) can be implemented using the same code and screen or interface across multiple software applications. Other features may require the same core code across multiple applications and platforms but differ in details. For example, an Account Creation feature may differ in details from one application to another depending the information that the account creation requires from the user. To that end, the software development platform of the present invention enables the user to customize a feature without modifying its core code and functionality and therefore without affecting its interchangeability between software applications.

Each feature provides an additional means to process data and/or interact with other applications and users. In the context of prototype generation for presenting a workable graphic demonstration of a prototype through a platform such as a browser, embodiments of the present invention do not necessarily need to generate source or assemble or generate object code from source code. In operation, the system will be operated as a software application that can interact with data, store and modify data, and have the application (running in object form) generate the prototype for interaction with the user via a browser for example.

Features of the software application may include for example, Account Creation, which enables the application to have users set up an account by filling out personal details on a form; Location, which enables provides the application access to the mobile device's location functions; or Push Notification, which enables the application to send notification to users when the application is closed. Typically, features provided in the graphical user interface for selection may be grouped by types of features. For example, the interface may provide a bundle of features deemed “Essentials” (which includes for example Account Creation, Search, or Two-factor Authentication), a “Finance & Payments” set (which includes Payments, Centralized Billing, or Automatic Renewal), or a “Customer Insight” (e.g., Review or Polling features).

In some embodiments, a subset of the library of features may be organized in pre-organized sets called templates. FIG. 5B illustrates graphical user interfaces 500 displaying a library of templates 550, according to an embodiment of the present invention. Each template 550 of the library provides the basic functional architecture and visual layout of the software project. In particular, the template 550 provides a predefined and customizable basic process flow process between a set of predefined and customizable features or functions of the software application. The library of templates 550 may be displayed on the graphical user interface 500 as a set of icons, a list, a drop down menu, or any other means of presenting a set of information on a graphical user interface.

In the embodiment illustrated, the templates 550 are grouped by types of software, such as mobile applications for mobile devices, web applications for website, marketplace applications that help buyers and sellers transact in real time, e-commerce application, applications for wearable devices such as apple watches or google wear, or any other types of applications that may be available on consumer devices. In the embodiment illustrated, the graphical user interface 500 further provides examples of templates within each grouping of templates. For example, the mobile application grouping may include a list of mobile application templates such as Uber, Snapchat, Quora, Tinder, or other popular mobile applications that a customer may want to use as a model to communicate requirements for their own application. A social media grouping for templates may include Facebook, Snapchat, Instagram, and templates of other social media applications. It should be noted that Applicant is not affiliated with the providers of the above applications and services whose structures may provide bases for templates in some embodiments.

After the user has selected a template 550, the user is provided with the opportunity to customize the software project by adding features to or removing features from the template. In some embodiments, the interface may display a set of pre-selected additional features specifically corresponding to the template. For example, if the chosen template is that of a social media app, the user may be provided with additional relevant features such as Private Messages or Take Photo. Thus, the system enables the user to build software by either selecting features individually (e.g., “a la carte”) or selecting a predefined set of features or a template, building upon the template by adding or subtracting features to form the software project.

Referring back to FIG. 4 , in some embodiments, the builder software 440 on the server 430 may further comprise a feature selector 455 configured to select a set of features based on input from the user. In such embodiments, the client device 410 may prompt the user with various questions for specifying the type of software application and broad set of features desired, rather than presenting the user with a list of specific features. The feature selector 455 is configured to translate the user's input into a set of features to be integrated to form the target software application.

After the selection of features, or the selection of a template and if desired, a set of additional user-selected features for the template on the graphical user interface, the features are transmitted to the server 430 from the client computing device 410. The template would be understood as discussed herein to include a set of predetermined interconnected features that correspond to a particular model. As described above, the selection of features may also be generated by a feature selector 455 that receives as input answers to prompts from the user interface and generates a selection of features therefrom. Upon receiving the selection of features from the client computing device 410, the builder application 440 transmits the set of selected features to the integration engine 445. The integration engine 445 is configured to assemble the selected features into an integrated build card of the software application. Specifically, the integration engine 445 is configured to receive a set of features, identify new or additional features from the library that may be required by the selection of features, automatically generate connections between the features of the set based on rules from the rules database and the attributes of each feature, and provide an editable visualization of the set of interconnected features or integrated build card. Elements of a feature that enable its connections with other features to form the prototype of the application are described next. The rules can include strength of feature associations, prioritized list per feature, conditional based on other selected features, or association based on phase of application use (e.g., checkout versus shopping), other rules, or combinations thereof.

FIG. 6A illustrates a feature 600 as a displayed screen of an application according to an embodiment of the present invention. As previously described, a feature 600 may include one or more screens and the illustrated feature comprises a single screen. The feature screen may include one or more display regions 610 and one or more interactive regions 640 (only one of each is shown to simplify the figure). The display regions 610 serve to display content relevant to the feature. The display region 610 may display text, animations, images, videos, or any information configured to be displayed by the feature of the application. The interactive regions 640 host interactive elements 650 that enable the user to interact with the application. Two types of interactive elements 650 are provided: input elements, and navigation elements. Input elements enable the user to provide information in the application. An input element may be a text box, a drop down menu, a radio button, and other forms of input interface elements. The navigation element enables the user to navigate to another screen in the application. In some embodiments, an interactive element 650 may be both an input element and a navigation element.

A particular type of interactive region 640, called hotspot 645 herein, is configured to host a type of interactive element 650 that serves to call another feature. That is, some interactive elements 650 are links or icons in a source feature configured to activate a target or destination feature of the application (which typically involves displaying another screen) when actuated. These interactive elements 650 are configured to call another feature are called sidekicks 655 herein.

FIG. 6B illustrates a representation of a feature 600 according to an embodiment of the present invention. The feature 600 is illustrated as a data structure stored in a database. The feature 600 comprises a layout element that defines the layout of feature screen, a display element that defines the functions of the display regions of the feature screen, an interactive region element that defines the functions of the interactive regions of the feature screen (e.g., interactive elements and hotspots), rules element governing how the feature may be called, and a core function element that regulates the substantive functionality of the feature (what it actually does).

FIG. 7 illustrates two features 700A and 700B as displayed screens, according to an embodiment of the present invention. The first feature 700A comprises a hotspot 745A in one its interactive regions 740A that hosts a sidekick 755B for the second feature 700B. Actuating the sidekick 755B in the hotspot 745A calls the second feature 700B. For example, the first feature 700A may be a Login feature of an application. The sidekick 755B hosted by a hotspot 745A on the Login feature may be a sidekick of a Forgot Password feature 700B, which is configured to call a Forgot Password feature 700B. Actuating the Forgot Password sidekick 755B (whether by clicking, long-pressing, swiping, or by any other action allowed and specified by the sidekick) thus activates the feature 700B.

A feature comprises a set of attributes that govern how it may be called. These attributes may be stored as metadata associated with each feature. FIG. 8 illustrates an exemplary hierarchy of attributes 800 for a feature that governs the feature's interaction with other features. In particular, this hierarchy of attributes 800 governs the action type that can call or activate the feature (as a target feature or destination feature) from another feature (source feature). The Action Type for the subject feature can be a single action or Multi-Action. A single action may include a tap, a long press, a swipe, or a drag. Multi-Action may comprise Navigation, input, output, and edit. Thus, if the action type for an exemplary feature were Single Action, Long Press, such a feature could only be linked to by a long press on an interface element linking to the feature.

Referring back to FIGS. 6A and 7 , a hotspot 745 in the interactive region 740 of a feature also comprises a set of attributes that indicate which features the hotspot 745 may invoke. More specifically, the attributes indicate the types of features whose sidekicks 755 or icons the hotspot 745 may host. Accordingly, the hotspot's set of attributes mirrors features' metadata that govern how the features may be called. For example, a hotspot's attributes may be single action, long press. This means that only sidekicks (or links) 755 of features that match these attributes (i.e., single action, long press), can be hosted in the hotspot 745 and therefore be called from it.

Each feature thus may comprise two sets of attributes that govern how the feature may interact with other features: a first set of attributes in the feature's metadata that determines its behavior as a destination feature, that is, which types actions may be invoked from a hotspot to call the feature, and a set of attributes that determines its behavior as a source feature, that is, which types of features one or more hotspots of the source feature can call. Table 1 illustrates an exemplary set of action types attributes for a feature or for a hotspot of a feature.

TABLE 1 Single Tap No Action Long Press Yes Swipe No Drag No Multi- Navigation No Action Input No Output No Edit No

The integration engine 445 (shown in FIG. 4 ) is configured to assemble or integrate the set of selected features into an integrated build card for the application based on the attributes for each feature (e.g., as described above) and a set of rules governing the inter-feature relationships or associations (as stored in the rules database). To automatically integrate the features of the application, the integration engine 445 accepts as an input the set of features received from the client device (which may include the selected template and any additional features). Specifically, the integration engine 445 receives a build card, which is an instance of the set of features that is instantiated from the selected set of features received from the development application 420 on the client device 410, and generates an integrated build card based on the received build card and the inter-features rules set.

The integration engine 445 may retrieve the set of rules used to integrate the features from a rules database 470 configured to define and store the relationships between features of the library of features. The integration engine 445 can be configured to store common feature interconnections or feature flows and present the user with suggested interconnections or flows. This can include suggestion of proximity of features to each other within a flow of screens or pages in the application.

In some embodiments, the relationship (e.g., connections or flow) may be stored in terms of probability of connections between the features 910. Other methods for storing or representing dependencies or relationships between features in the database are contemplated.

Thus, for each feature, the integration engine 445 automatically identifies which source features should be provided with links to the feature, based on the rules database (i.e., the graph database, in some examples). The integration engine 445 may also automatically determine destination features whose links the feature should host. The integration engine 445 is further configured to identify new or additional (i.e., features not selected by the user) that the rules database indicate may be associated with features that were selected by the user. Further, for each feature still, the integration engine determines links to which functions of the feature, and the form of those links in the source feature based on the attributes of the source and destination. For example, in an eCommerce application whose feature selection by the user include a Product feature that displays a product for sale and a Checkout feature to checkout purchases, the integration engine 445 may automatically determine the Product feature should call the Checkout feature based on the rules database because the rules database associates the Checkout feature with the Product feature; this may mean that a link to the Checkout feature should be placed in an interactive region of the Product feature to provide the ability to check out. Further, within each source feature, the integration engine 445 may cause the feature to provide a logical and optimal layout for the screen (e.g., size, shape, number, functionality of display regions and interactive regions) to accommodate the destination features whose links the source feature hosts, based on the attributes of the source and destination features. Thus, the integration engine 445 may automatically determine that the checkout link should be in the form of a button rather than a check box.

The integration engine 445 subsequently generates a screen flow view of the integrated build card on the graphical user interface of the client device. FIG. 9 illustrates a screen flow view of the integrated build card 900 according to an embodiment of the present invention. The screen flow view illustrates the software project as a set of features 910, each represented by one or more screens 910. The features 910 of the screen flow consist of the features of the selected template and set of additional selected features that are logically and automatically connected together by the integration engine 445 based on the rules database 470 and on the attributes of each feature 910 of the feature set. The screens 910 are linked by connectors 920 such as lines or arrows 920 that indicate the interaction between the features 910. The connectors 920 may be of various types and colors to represent different types of interactions between the screens 910. For example, a connector 920 of a certain color may indicate that the destination feature is called by a single action gesture (e.g., a tap), whereas a connector of another color may indicate a multi-action gesture. In addition to the color of the connectors, other visual indicators (thickness, dashed lines, etc.) may serve to indicate the type of interaction between the source and the destination feature. The screen flow view enables the developer to visualize the interactions between the various features 910 of the application.

The system further enables the user to customize the prototype by editing the screen flow. Connections or navigation 920 between the features or screens 910 can be altered by changing the source of an arrow, its destination, or both (interactively using graphics), as well as the type of arrow (type of connection). When a new connection is formed 920, the integration engine automatically determines and provides the appropriate link (i.e., the type of connection) to the destination feature in the source feature based on the attributes of the source feature and destination feature. The integration engine may further adjust the layout of the destination feature to accommodate the link. The attributes of each of the source and destination feature may govern which connections 920 are possible. For example, if a particular feature can only accommodate three links to destination features (for example, because of limited space in the interactive regions of the source feature), the screen flow may not allow the addition of a fourth destination feature link to the source feature. Alternatively, the source feature may switch to a different type of interface elements (e.g., from a set of icons to a drop down menu) to accommodate the additional link. The customer or user may also edit individual features 910 to modify the layout, change the size and shape of the display and interactive regions and elements, add or subtract the same as well as links to destination features.

The integration engine 445 saves each edit of a feature and alteration of the connections 920 or navigation between features 910 in the rules governing the relevant features of the integrated build card. In particular, the integration engine translates each edit to a feature on the interface into the database entry for the instance of the feature. This enables the integration engine 445 to build the integrated build card from a set of edited features that reflect the edits of the customer (e.g., changes to the features and connections between the features) made on the screen flow as described above. After the next integrated build card is built, reflecting the changes made on the screen flow, the user may further alter the screen flow (which is regenerated based on the saved edits) to revise the application project and build a subsequent prototype. This iterative process enables the customer to observe the result of each change and progressively fine tune the project to project to meet their specification.

FIG. 10 illustrates a screenshot of a prototype 1000 of the software application according to an embodiment of the present invention. The prototype 1000 is an interactive representation of the application on a virtual platform provided in the graphical user interface. The prototype 1000 enables the developer to use and test the initial version of the application prototyped according his selection of templates and features. The prototype 1000 is generated by a prototype engine 450 (shown in FIG. 4 ). The prototype engine 450 generates the prototype based on the integrated build card. Specifically, the prototype engine 450 accepts as an input the set of instantiated features as modified by the integration engine (if edited) and the connections between the features as identified by the integration engine 450 and modified by the user. The prototype engine logically arranges the features of the integrated build card and populates their display and interactive regions according to the edited attributes and rules to provide an operable visual interactive simulation demonstrating a functional prototype of the desired application. The prototype 1000 generated by the prototype engine 450 and transmitted for display by the graphical user interface on the client device is thus a clickable or navigable prototype of the customer's application, in some embodiments. That is, the interface elements of the prototype simulate the operation of the actual application, to the extent possible. For example, a button linked to another feature will bring up that feature when clicked upon or otherwise actuated by the user on the prototype. After operating the prototype, the user may refine the application by returning to the screen flow to edit the integrated build card (add/remove/edit features and their connections) as previously described.

In some embodiments, the build card, the integrated build card, or both, may serve to update the rules database 470. Specifically, the aggregate selections of multiple clients and builds can provide or enhance statistical data on the preferred connections between features as recorded in the rules database. In some embodiments, feature dependencies may be crowdsourced from the historical selections of users of the system. Thus, inter-feature information use in the rules can include the frequency or probability of selecting a specific feature when another is selected. The history may involve many different interactions including inter-screen connections and edits thereof. Other mechanisms for updating the rules database based on the aggregate history of build cards are contemplated.

The editing and selection by the user to adjust or create the described instant prototype can preferably be incorporated into the development process. In particular, the selections may automatically be included in the source code generated for the software application.

Pricing can be integrated using a database in server 430 that contains pricing information and a pricing engine as part of builder application 440 that is configured to determine or identify pricing using the database and as a function of the selected features for an actual software application sought to be developed by the platform.

Server 430 can also have a database in server 430 that contains information about a plurality of software developers including communications address for each and integration into the builder application 440 using communication connection and login credentials. Server 430 can include communication platform using the information from the database to operating a work flow through the various phases using one or software developers that are integrated into the platform to provide an efficient work flow.

Embodiments of the present invention disclose a system and method that automate aspects of developing software applications including the prototyping process as illustratively described herein. Embodiments of the present invention involve creating a graph or graph database that involves a computer system that is configured to collect discrete information as defined nodes and edges as part of this process. For example, a software development platform can be configured to include an interactive online interface for receiving a customer software application project and engage in that process to completion. The platform can provide an engagement process in which the customer through interactive software interactions (or possibly sometimes human interaction in some instances) can specify the functionality and operating characteristics of the desired software application. The platform can include selected features, manually or automatically, that work through the software development process with the customer and is configured to operate to develop the software for the customer through the use of a team of software developers and other included software and hardware infrastructure. In some embodiments, the platform is configured to automatically generate the software application or to combine the use of developer with the automatic generation of the software application.

The platform can handle different types or categories of applications and be configured to accept, for example, many projects. An advancement that can make a material and significant improvement is that the platform can be configured with defined nodes and edges that correspond to entities and relationship. The nodes and edges are used to create a graph database representing the information that is being collected by the software application development platform. The resulting graph database provides more advanced, faster, granular, predictive, and more accurate system for tools or features within the software development field and the platform. The structure of the graph schema and graph database provides improvements in speed such as to provide real time responses that are not otherwise possible using conventional solutions in this field of technology (software development platforms). This incorporation materially improves the functionality of the platform and the development process through capitalizing in identifying valuable pathways and interrelationships that are discovered from the graph.

As illustrated herein as examples which can by themselves be particularly suitable for use. Nodes can be defined by the platform for example as the following types: template, build card, developer, feature, problem statement, and CPE/CTE (client product expert/client technical expert). Nodes can have predefined attributes such as complexity, price, or time, the value for which can be added to the node by the platform based on customer interaction, by an automated process, or by tracking actual performance such as tracking a project and automatically entering the time when a feature was completed. Edges can be defined to describe a limited set of relationships between nodes. A limited set of edges can be defined to categorize different types of node-node interrelationships. Illustrative or examples of information is provided in the figures of edges, which can also be particularly valuable in implementation. This structure of nodes and edges can allow the platform to automatically and in a uniformly consistent way ingest the (end to end) software development process (including a range of attributes such as prices, timeline, skills, etc.) as carried out through the platform and are quickly defined for progress in to the next phase of development.

The platform through aggregation creates, stores, and updates the graph database including the nodes and edges as per the defined characteristics of the nodes and edges. The resultant graph through aggregation can result in a highly valuable resource in improving the platform and software development such as by providing software applications that have fewer bugs.

The system can be configured to permit different types of software queries and propagation to provide different features such as to automate platform features and support software development and platform operation. For example, as shown herein, a feature can define a node and a range of software features can be saved as nodes in the graph database. The system can store edges, among which it can store edges that specify that each project has an edge to another feature node when those two feature were included in the same software development project. This can for example be accumulated for many projects (e.g., thousands, hundreds of thousands, etc.). Because each project may include many different features, the resulting node interrelationship can be complex in a large order of magnitude. The features can have edges to other types of nodes such as developer nodes for the specific developer that developed that feature for that project.

As a base case, the node/edge relationship captured for features in projects can be queried. For example, a potential new project has been selected (e.g., by a client) to include three different features from a menu to be included in the client's project. The platform can query the graph database and the selected features can be applied as a query to the graph database that in response will for example traverse only through paths that includes the select three nodes, and will further traverse those subgraphs in the found paths that contains the three nodes to identify other nodes that are connected to all three of those nodes (when all three of those nodes were included in another project). A query to the graph database can also involve a query to an embedding generated from the graph database and representing the graph structure in computer operationally simpler construction. The query may further establish an algorithm that may filter nodes that are found through the traversal to a set that meets a threshold (e.g., this fourth node was included every time these three nodes were include, or this fourth node was include a large percentage of the time) indicating a likelihood of valuable software development and functional affiliation. To amplify, this can involve 10 selected features and can also include variations where the query is varied to find any 9 of the selected features and then identify the related nodes in that path for use in the platform as a suggestion or automatic incorporation. Other analysis at the same level or more complex can be obtained quickly with reliable predictions based on the aggregated graph and the values of nodes and edges. One intuitive value is that providing reliable information to clients can provide higher level of credulity and trust. It can also provide better software performance since available features (catalogue of features on the platform) are automatically scored and included in proper association (such as for a particular new or proposed project).

If desired, the system may have a visual interface that permits user to interact with the nodes and edges (e.g., to apply a query) but such a feature is not required.

The platform can be a cloud service that permits the user to interact with the platform through graphical user interfaces to complete the different stages of the application development process. That would generally be understood to involve a combination of one or more computers, software implemented on the one or more computers that configures the computers to provide a specialized application, and online, Internet website access, to the functionality through a (conventional) browser or in some cases, a software application (e.g., a mobile app).

The platform can be configured to allow the user to select the desired features as a preliminary step in order to specify the requirements for the desired custom software application (the scope of the software project).

Graph database 480 of FIG. 4 is included as of the platform and related processing can be performed by server 430 and software running on server 430 such as the integration engine 445. The graph database stores nodes and edges that represent corresponding entities and relationships between entities. Graph database 480 can be implemented on its own server and a copy of the graph database can be at discrete times provided the platform to provide services using the graph database.

The software development platform is configured to collect data from activity in the software development platform such as a project scope process, pricing process, and project development process in accordance with platform-defined graph data structures. The data is collected is tapped or copied from the existing operation of the software development platform to collect historical data about activity in the platform and interactions to aggregate such data. The graph data structures comprising a plurality of different types of nodes representing entities and the node types comprising template, feature, and other node types such as developer or problem and each node type having a set of defined attributes, and different types of edges that represent interrelationship between entities.

The platform is configured to generate and store a graph database 480 comprising the nodes and edges created from the collected data in the operation of software development platform and is configured to reuse existing nodes and edges, add new nodes and edges, and adjust individual attributes assigned to each edge based on new data. For example, a new software project may include a login feature and the login feature was previously included in the scope of other previous projects, the platform does not need to add that node to the graph database since it was previously used. The edges are defined relationships between different type of nodes. Attributes can include a count or frequency associated with each edge stored in the graph database and represent how many times that the same edge connection (between the same two nodes) were found in the software projects that have been loaded into the graph database. The graph database manages large scale data in a different way than generally used databases.

The platform is configured to continue to load software projects (e.g., sets of features and/or templates into the graph database) and it can if desired include nodes or edges for related activities. The software development platform and related information is updated as new software projects are created or initiated in the platform. The software development platform is configured to issue a query to the graph database and in response, receive query results from the graph database or from related components that it uses to control one or more parts of the operation of the platform (e.g., an action within a process).

The software development platform is configured to implement one or more algorithms configured to traverse nodes and edges in the graph database in accordance with one or more criteria of an algorithm. The algorithm can be selected to correspond to the query, which in this case is directed to providing feature recommendations. The algorithm can traverse the knowledge graph to identify different paths starting from a node through its connected edges to other directly connected nodes and similarly continue until a criteria of the algorithm is not met (which causes that traversal to stop). So, for example, a path may involve node1-edge1-node2-edge2-node3. The algorithm identifies paths relevant to the query and stops traversing the nodes or edges when the criteria is not met. The algorithm can start with a different node in the graph to apply the algorithm and collect information such as paths can repeat the procedure over the graph database to discover the graph structure, nodes, edges, and/or paths that meet the criteria. The application of the algorithm can be implemented in advance to collect the resultant path or other information and the results can be stored for handling later received queries. The software development platform can be configured, in response to the query, to control a user interaction in the project scoping process comprising displaying an option that suggests a feature to include based on the structure of the graph database.

Embodiments of the present invention implement a framework that takes advantage of the semantic relationships between diverse data points in software development platform's database. This is achieved by storing related data in a graphical structure. This allows the platform to enhance knowledge around each data-point by leveraging their connection with other data-points. FIG. 11 is an illustrative representation of an example of graph database containing different types of nodes (the circles) and edges (the lines connecting circles). Six types of nodes are illustrated in FIG. 11 including skill 4402, feature, project, CPE, template, and developer. Each node is for a different such entity so for example the two developer node be for developers John Smith and Jane Blue. The edges are shown to be directional and they demonstrate for example developer 4406 has a certain skill 4402. The platform can be configured to apply different traversal algorithms to quickly identify information (or set of relevant paths) and potential associations by traversing the nodes and edges of certain types.

The configured graph database incorporates nodes and entities from different processes or aspects of the platform which allows for interrogation and discovery of interrelationship and potential associations from paths containing connected nodes and edges across the different tasks, processes, or relevance. The graph database is not solely focused on the software elements that together form the software application for a software project but extends into other areas in the software platform and in so doing, provides a greater depth of performance. For example, FIG. 12 is an illustration that shows an implementation of nodes involving different aspects of the platform. FIG. 12 illustrates that the defined node types can be template, project feature, developer, CPE/CTE, and problem statement. Boxes shown in the diagram contain an illustrative set of attributes for each node type. For a particular project, the collected data that is instantiated in the graph database can include the range of all of the types of nodes and the edge connections.

In preferred implementation of embodiments of the present invention, four or five different entities (or nodes), the fifth being creator, are implemented to configure the software development platform are selected and used in the graph database process. The entities and corresponding node types are:

-   -   1. Feature: Features are the atomic unit of a real-world         application that provide functionality to the app. The data         around features is sourced from a content management database         (part of the platform, which can be in features database for         example). which can include the features database, that contains         preconfigured information such as meta data including         connections or links to other features. A feature is also         defined further herein.     -   2. Projects: A project is a collection of features. These are         used to understand how some features combine to form a real         world application. We source the data of our historical         projects/build cards from a database that stores this historical         information.     -   3. Templates: While projects contain some level of noise in         them, templates are very well structured collection of features         that form a real-world application. Also, the build card         generation process allows a user to base their project/app on a         template, it provides a fair amount of information around the         type of a project. The template data is sourced from a database         that contains the template to feature mappings, which can be in         the features database. Template is also further defined below.     -   4. Problem groups (or Problem): Problem groups are groups of         templates that solve similar types of problems. This gives us an         insight into how features combine towards solving a particular         kind of problems. The data around problem groups is sourced from         the problem-groups table in a platform database (e.g., features         database).     -   5. Creators: Creators or Developers are the key workhorses in a         client project and are assigned to a project based on their         skill and proficiency—(skill level) using the resource         allocation tool (RAT). During the course of the project,         creators are then assigned to several features—stories by the         CPEs, information of which is recorded on a tracker process.

Graph schema that is defined in the platform and applies to the data is used to create and refresh the graph database. For example, the below tables show an example of graph scheme (the entities/nodes being explained above):

A B C D E F 1 Entities Feature Project Template Problem Creators 2 Attributes builder_id builder_id builder id builder_id builder_id 3 name name name statement email 4 bundle_id build_card_id description vendor_name 5 complexity created date status country 6 interface_type updated_date created_date 7 price start_date total_hours 8 time end_date communication 9 is_core cost responsiveness 10 description security_deposit delivery_owners hip 11 question timelines skills: expertise score 12 embedding status nb_tracker_logins 13 brief nb_cpe_feedbacks 14 speed rejected_story_ratio 15 squad on_demand_price 16 rat_score_v2 17

Graph schema can include relationships between nodes such as:

A B C D 1 Entity 1 Entity 2 Relation Relation Attributes 2 Feature Feature feature-feature — 3 Project Feature project-feature — 4 Template Feature template-feature — 5 Project Template project-template — 6 Template Problem template-problem — 7 Creator Project creator-project communication, delivery_ownership, responsiveness, skill_name, skill_expertise, skill_score Relations can also have their own set of attributes such as a count for an edge of how many times the same pair of nodes are connected with that edge. Below are the details for each relation,

-   -   1. Feature—Feature Connections: The existence of an FFC relation         between any two features signifies that those features are         usually linked to each other in a real-world application. This         data is sourced from database that stores “hero-sidekick”         feature mapping data (stores information that includes link that         are commonly or usually linked by human design and/or automatic         determination). The database may also record as part of an         attribute information about how many times the same pair of         nodes are connected.     -   2. Template—Feature/Project—Feature: Templates and projects are         related to features through this relation. This signifies that         the connected feature is a part of that project or template. In         terms of a project it means that the connected feature is a part         of the build card of that project. In terms of templates, the         connected features simply is a part of the feature pool that the         template is made up of.     -   3. Project—Template: This relation connects projects to         templates. Any user that lands on a studio interface for         designing the application and starts to ideate their project,         they are presented with an option to base their app on a         pre-existing application template. If the user decides to base         their app on a template, it gets added to their build card. This         relation signifies that a particular project is based on the         connected template.     -   4. Template—Problem: A lot of application templates are a part         of some problem groups. This is based on the industry they         belong to and the problem that they solve. For instance, the         application template of Uber solves a city's transit problem, so         it belongs to that problem group. This relation connects         application templates to the problem groups that define the         problems that the particular template solves.     -   5. Creator—Project: The existence of a creator-project link         signifies that a creator was assigned to a given project.         Moreover, each creator-project edge contains following         attributes which provide a granular view of the allocation:

A B 1 creator-project Description 2 communication sum of CPE feedback score for a given project. 3 delivery_ownership sum of CPE feedback score for a given project. 4 responsiveness sum of CPE feedback score for a given project. 5 skill_name Skill for which creator was assigned to a project - ′ROR′ etc 6 skill_expertise 7 skill_score

With respect to recommending features, the platform is adapted to provide the advanced capability using the graph database by being implemented in that process with the above four or five nodes and relations. These are the core or primary pieces that are operated on in the process. Other nodes or relations may exist in the platform. In preferred embodiments, the graph database algorithm and related processes for feature recommendation is configured to apply operations or algorithm on this 4/5 nodes and 4/5 (fifth being creator project) relations such as in the below described knowledge graph algorithm and embedding pipeline.

FIG. 13 is an illustrative representation of an implementation of a subsystem 6600 of the platform. It can be a portion of an implementation of the platform. Subsystem 6600 can include data ingestion 6602 wherein raw data is collected from the internal activity of the platform (e.g., data taps that collect data for use in the knowledge graph). Data ingestion uses predefined graph data structures to create nodes from the raw collected data. As shown, the node types are projects, templates, features, and problems. Other nodes such as creator can be included depending on objectives. Data ingestion also uses predefined data structures to create edges or relations from the raw collected data. As shown, the edges (relations) are project to template, templates to problems, features to projects, and features to template. Additional edges can be included. In knowledge graph stage 6604 the platform creates or updates the knowledge graph (or graph database) using the nodes and edges created from the collected data during data ingestion 6602. The knowledge graph is copied to the cloud for use by software clients. Clients 6606 are configured to query the knowledge graph to provide certain functionality. Clients 6606 include a feature recommendation client that for example, sends a set of features selected by a customer for a project to the knowledge graph and in response the set of features are applied to the graph database and one or more recommendation for other features that are found by the knowledge graph is identified and communicated. To clarify, a new project can include a template or problem and in turn these include one or more features (that embody the template or problem). In addition, the traversal algorithm can include the use of particular node attributes as basis for whether to traverse or identify paths (or groups of connected nodes and edges). For example, features may have an attribute of advance, intermediate, and beginner. The platform can for example apply an algorithm that traverses only intermediate features combined with some other attribute to quickly generate relevant information that can for example be used to control the design or operation of the platform.

Now with reference to FIG. 14 , an illustrative diagram is provided that demonstrates one type of query, response, and graph database algorithm that can be applied to provide an improved and advanced software development platform. Plane 7002 is a conceptual representation of the domain for a node type, which is in this case are features. The nodes in plane 7002 represent different features that are available or have been deployed in the software development platform to design or scope a project. Nodes are not the source or object code for that particular features but represent that entity in name and values of the attributes that are associated with it. If desired, each node can be linked to its corresponding source code (file) or object code (file). Plane 7002 includes nodes f1 7004, f2 7006, and f3 7008. Plane 7010 is a conceptual representation of a customer's build card (one in the process of defining project scope, selecting templates or features for the project). The customer, as shown, has interacted with the software development platform to selectively add features f1 and f2 to the build card. The platform, preferably in response, queries the nodes and edges of the graph database, for example by sending the customer selected nodes to the graph database. The graph database and platform can be adapted to receive and handle this particular of query. The graph database applies a corresponding algorithm, in this case additional feature recommendations to generate output from the graph database, which can include related information stored in the database. There can include having different algorithms adapted for different situation that are configured to apply a different operation or analysis on the graph database (e.g., node traversal or identify similar nodes).

In this situation, of FIG. 14 , the platform by applying the algorithm determines that customers that chose f1 and f2 often also chose f3. This as mentioned can be based on the number of times (an attribute) those edges were previously assigned between those nodes (in 10 past project or 100 past projects). FIG. 14 illustrates that f1 7004 was selected for a build card along with f2 7006, f3 7008, and f4, and f2 7006 was often selected for a build card with f1 7004 and f3 7008. The diagram illustrates that the graph database using the algorithm would be able to determine that f3 7008 is “linked” (e.g., pointers, software parameters, logical structure) to the two features in the build card and can generate an output identifying f3 as an additional feature (suggested feature) for the user to add (or to automatically) add to the build card 7010. This may appear simple but in the context of large scale data set and a software development platform involving many features and significantly more ingested projects, the determination is complex and difficult to determine in known software development platform technology.

With reference now to the functional block diagram of FIG. 15 , in implementation the platform can be configured include a server on which the graph database resides. The platform can be configured to include a method that updates, maintains, and delivers the services to platform processes. As shown, data is provided in 8002 for incorporation into the knowledge graph where the data is in different planes (categories or types of nodes) such as project, feature, template, and problems. The content management system that stores data related to feature connectivity is provided 8004 within the platform in order to provide such data. At step (or function) 8006, the provided data from 8002 and 8004 are ingested periodically and saved. At 8008, the platform is configured with graph scheme and includes methods for adding new node and edge types. The platform is configured at 8012 to create or refresh the knowledge graph instance and save it. The is performed using the graph schema and ingested data to create or refresh an existing graph database with the new data. The knowledge graph is saved in Object 8014. The platform is configured to use this as the resource for continuing to update the knowledge graph without affecting related services that interact with the graph database. The platform would want to continue to update or refresh the graph database while also providing a live steady resource for use and interaction in the system. The platform is configured to isolate or buffer the ingestion, creation, and refresh of the graph database so that for example is running independently on a server separate from platform operation in providing processes to customers, developers or others. The platform is configured to store the diverse large scale data ingested and in accordance with the graph schema in the graph database which contains a wide range of nodes and edges comprising a wide range of software development entities and relationships on the software development platform. The graph database and related or supporting functions or functionality is specifically adapted for software development platforms and feature recommendation such as by having graph schema providing for the node types identified herein.

To provide services 8016, a script is used to copy the graph database in its then current form after recent ingestion, creation (or refresh) from the graph server, from object 8014. In services 8016, the copied graph database is loaded into the memory for the services and at 80022, the platform is configured to interact with the loaded graph database to provide feature recommendations. Once copied it is made “live” for use in the platform. Module 8024 is implemented to allow the services to interact with the graph database in the production phase of the database.

The nodes and edges can be configured to be directed such that edges point in a direction such as from project to features that were included in that project.

In some embodiments of the present invention, node embedding is implemented from the graph database. For the purposes of discussion and operation, the node embedding and related structure or method is considered part of the graph database functionality and related elements. The platform can rely on node embeddings derived from the knowledge graph. The knowledge graph is likely in practical implementation in constant evolution, which means that relevant embeddings are themselves in constant evolution. In addition, each service or software client of the platform may rely on a different setup for the embeddings. For example, one application may require one algorithm to generate embeddings (e.g., Metapath2vec) while other applications will require another algorithm to generate embeddings (e.g., Graph Sage). The operation of these algorithms can be located from Internet websites.

From a production point of view, platform implements a pipeline that regularly updates the required embeddings for each application. From a development point of view, the platform is configured to create a package that allows any relevant developer of a particular application to generate embeddings on the fly given a particular setup.

More specifically, from a production perspective the platform is configured to be implemented to:

-   -   whenever the knowledge graph is refreshed for an application or         service (application or service in this context referring to the         software in the platform that uses the knowledge graph to         provide one or functions or capabilities), the platform can         determine if the knowledge graph changes also affect the         embeddings required for the application or service (e.g. new         entities added or new edges added);     -   different embedding setups are provided for different         application or services, and when refreshed the right embeddings         are uploaded to the right application or service; and     -   include embedding generation separate from the primary operation         of the platform comprising, for example, project scoping         process, pricing, project management, and testing in order not         to slow the performance of the platform and to avoid the         platform breaking down.

Preferably, the platform is configured to trigger the training of the embedding locally. The package software components and method(s) that implement this capability should be very simple to use and preferably only requires as input the algorithm name and a hyperparameter. In a current embodiment, each application or service in production has a configuration file in the form of a Json file: the Json have two entries, the first entry is the algorithm name (e.g., Metapath2Vec) the second entry is itself a json that specifies the hyperparameters of the algorithms (e.g., metapath_dict, window_size, etc.).

There may also be a readme file in the embedding package specifying the list of hyper parameter names corresponding to each algorithm name. Once the pipeline is triggered the first steps consists in fetching the configuration for each application or service to form a master configuration, run embedding generation for each configuration, for each configuration in the master configuration file, preferably first verify that the required data for the embedding generation changed and preferably only in this case run the embedding generation and upload the resulting embedding to memory thus replaces the old embedding for this particular configuration.

Now with reference to FIG. 16 , an illustrative generation pipeline is provided as implemented in some embodiments of the present invention, the pipeline is configured to use the graph database to generate different node embeddings that are adapted for different desired services, clients, or applications. The pipeline or components thereof can be implemented in combination with graph database in order to provide computational simplification, higher relative speed of information retrieval while maintaining accuracy, and adaptability or dynamic ability to be tuned to different needs in the platform and provide on-demand support due to the pre-generation of the embedding prior to the need for handling a query or other analytic operation. The embedding can also be loaded into memory or tables that are not graph databases which are easier to store and perform mathematical operations on (e.g., a conversion from graph database to n-dimensional vectors that are better adapted for computer operations). In operation, the platform is configured to provide feature recommendation in real time in response to a query for a recommendation comprising selected features. This can be performed for example using the graph database and embedding arrangement. Real time refers to instantaneous or immediate response in relation to the receipt of the query.

Pipeline 900 can include control 9004, representation learning service 9006, embedding central repository 9012, and application (production branch) 9014. Representation learning service 9006 can include configuration selection component 9008 and embedding generation 9010. Control 9004 comprising one or more control commands that trigger or control the operation of the pipeline or elements thereof.

Configuration selection component 9008 is configured store different algorithms used to generate embedding. The algorithm can be specifically selected for example a corresponding platform service or software client such as feature suggestion. The configuration selection component 9008 includes hyper parameters that are parameters that store configuration information for the parameters. Each stored hyper parameter is used to configure a corresponding algorithm to be adapted to provide the desired functionality. The hyper parameter and algorithm (or link to algorithm) can be stored and fetched from application production branch 9014.

Embedding generation uses the selected algorithm configured in accordance with the hyper parameters to perform node embedding by applying the selected (configured) algorithm to the graph database and the algorithm generates an n-dimensional vector space (n represents the number of columns of vector). The n-dimension vector reflects the structure of the refreshed or created graph database (wherein there is each node is represented by its corresponding vector) and contains data value that are adapted using the corresponding algorithm to identify or communicate similarities, explicit relationships, likely relevant edges, similar nodes or similar paths (a path being a series of node and edges that form a connected chain that can be traversed without breaks). The pipeline 9002 can store the different node embedding in central repository 9012.

With this approach, the provider of the platform can have its developers be free to use the information in the knowledge graph in many different ways and free to select and configure an algorithm for the node generation that best suits each new service or software client. The developer can select the algorithm and its hyper parameters, and can load that into the application production branch 9014 or storage associated with pipeline 9002. The pipeline can run the different node embedding by fetching its configuration file (the algorithm and hyper parameters) and update the node embedding by applying the adapted/tuned algorithm to the current knowledge graph. The service or software client can then retrieve the corresponding nod embedding when the service or software client is executed in the platform. This can provide a robust and highly efficient and quick mechanism for providing the depth of intelligence in a vast and diverse knowledge graph to many diverse set of services or software clients on the platform dynamically or on demand. When implemented in combination with system of FIG. 15 , the pipeline is operation on the production copy of the graph database in services 8016 to provide the node generation as opposed to the graph database stored and maintained separately that is used for refreshing or creating the graph database. This may cause the graph database to potentially be not as current but it avoids conflicts or interference in operation if for example the graph database is used simultaneously for both. It should be understood that in some embodiments, simultaneous use is contemplated.

As such, the software development platform can be configured to include embedding generation that generates an embedding comprising a plurality of n-dimensional vectors that in accordance with an embedding algorithm represent the graph database, each n-dimensional vector corresponding to a node in the graph database and comprising vector values based on relationship to other nodes in the graph database. The software development platform can be configured to store a plurality of different hyper parameters corresponding to different software tools (services, software clients such as feature recommendation) on the platform. As explained above, the software development platform can be configured to control the embedding generation with the hyper parameters and generate different embeddings and store the different embeddings corresponding to different software tools.

The software development platform can be configured such that a query (a query seeking information from graph database) is applied to the embedding to generate an output for the control of an operation, display, or recommendation. The software development platform can be configured to include a software tool that suggests a feature to add to the software project based on the embedding. By another example, the software development platform can be configured to include a software tool that determines another control or action over the software such as a connection or link being added between two features in the catalogue (in the feature database as part of the predefined characteristics of the feature prior to the design process) (and displays screen to show and/or carry out the action) based on the corresponding embedding. The software development platform can also be configured to control or suggest a portion of software project to be assigned to a particular developer based on the embedding (values in the n-dimensional vector). The graph database can be used as part of the prototype development configuration for feature recommendations, connecting features, controlling the connections, and other functionality.

As such an integrated online software development platform integrates among its many functionality and diverse data machine learning across that is flexible and on-demand for incorporating machine learning tools that control the operation of the platform such as to control options that are presented. The architecture can also be implemented to control the arrangement and/or connections between features in a software project or other design or development functions using the graph database and/or embedding technology.

With reference now to FIG. 17 , the process involving knowledge graph and embedding is further described. At step 1002, the platform applies an algorithm to the knowledge graph. The algorithm performs random walks through the knowledge graph to generate a corpus. The corpus refers to paths (node-edge-node) sequences in the graph that meet the traversal requirement of the algorithm. The collection of those resulting/identifying paths is the corpus. The algorithm can be configured to limit the number of traversals to for example 40 nodes. At step 1004, the platform trains parameters of a skip-gram model over the corpus to generate the embedding. The method of FIG. 17 , preferably provides node embedding generation through Metapath2vec, which can be found at Dong, Yuxiao, Nitesh V. Chawla, and Ananthram Swami. “metapath2vec: Scalable representation learning for heterogeneous networks.” Proceedings of the 23rd ACM SIGKDD international conference on knowledge discovery and data mining. 2017, which is incorporated herein by reference in its entirety.

With reference now to FIG. 18 , in operation, to receive a recommendation, a list of selected features can be transmitted (as a query) to the knowledge graph capabilities. At step 1102, the platform retrieves embedding (vector), that has been generated, for each selected feature. At step 1104, the platform calculates pairwise dot products between the embedding (vector) of each selected feature and each feature in the feature database of the platform (or depending on situation some subset thereof or all features). At step 1106, the platform determines the score of each feature (not selected features in the catalogue or available on the platform). The platform averages the dot product each feature in the feature database (obviously not included a selected feature) with each selected feature over all of the selected features. For example, if the customer (in a very oversimplified example) selects f1 and f2 and the catalogue includes f3, f4, and f5. The process (for the score f3) involves the dot product of f3 and f1 and determining the dot product of f3 and f2, and then adding those to results and dividing by two (to obtain the average). Other implementations are contemplated. At step 1108, the platform determines the feature in the feature database that has the highest scope and selects it to be the feature recommendation. In some embodiments, the top so many such as two or three can be selected. In preferred embodiments, as described, collaborative filtering based recommender is implemented using the graph and embedding. Embodiments of the present invention describe particular implementation details such as graph scheme, algorithm/embedding (for traversing and determining vectors), and/or node types that are particularly suited for feature recommendation in the field of technology. Other application or tools are not excluded by the discovery or discoveries.

In some embodiments, the platform may include a plurality of different nodes in implementation the recommendation feature, the platform is configured to operate only certain types of nodes in the graph database such as project and feature nodes to provide the recommender tool.

FIG. 19 is an illustrative method that is configured to automatically identify and connect features for a prototype and for creating a running version of the prototype (immediately after the user selects features for the software project). It can be a first version of the prototype. In the method, in the central block, the figure includes a flow diagram describing the structure of the link prediction model used in the prototype generation such as a prototype generation API (Application Program Interface). In general, link prediction model predict whether a link between a first feature (the source Feature) and a second feature (the target Feature) should be present given that a certain template (or group of features) was selected by our user. The model performance is quantified using, for example, the F1 score, a known metric to measure the performance of a classifier.

Input to the model is the current build card, which contains the templates and features chosen by the customer using the platform for the customers proposed software project. In order to make the features and/or templates digestible by numerical algorithms, the method computes a numerical representation of these entities using embeddings. As mentioned, embeddings generate vectors or numbers that meaningfully represent the inputs. For example, if two features are similar, e.g., Login and [social network] login, then the numbers that represent them are also similar. These embeddings are computed using, in this example, the Metpath2vec algorithm implemented in the Stellar graph library in Python, which runs on top of the platform's knowledge graph (BKG). As shown, the algorithm used to predict if two features should be linked or not is LGBM (Light Gradient Boosting Machine). LGBM is distributed gradient-boosting framework for machine learning. This is one implementation as an example. It can be implemented using the LightGBM library available for Python. This algorithm is based on an ensemble of decision trees. The reason why we use the Light version is for scalability and performance purposes. The model output is a binary decision state whether the pair of features presented as an input should be linked or not. The output is used to automatically connect or link selected features for the purpose of configuring an operable prototype (being able to interact to move between features, operate prototype version of feature, or other actions. As such, the method using knowledge graph, an embedding from knowledge graph for this function, and classifications (link or not link) to configure or complete a prototype for the customer to experience with the platform (e.g., without requiring the user to make the connections manually using the interface at least for an initial prototype or without requiring the user to decide or connect 90% of the links).

Each of the system, server, computing device, and computer described in this application can be implemented on one or more computer systems and be configured to communicate over a network. In one embodiment, the computer system includes a bus or other communication mechanism for communicating information, and a hardware processor coupled with bus for processing information.

The computer system also includes a main memory, such as a random access memory (RAM) or other dynamic storage device, coupled to bus for storing information and instructions to be executed by a processor of the computer or computing device. Main memory also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by a processor. Such instructions, when stored in non-transitory storage media accessible to processor, configure the computer system into a special-purpose machine that is customized to perform the operations specified in the instructions and provide or be capable of features and functionality described herein. The processes described herein can be implemented as computer instructions executable by the processor of a computer of computing device to performs described process steps the computer instructions can be saved on nonvolatile or nontransitory memory for providing such implementations.

The computer system further includes a read only memory (ROM) or other static storage device coupled to bus for storing static information and instructions for processor. A storage device, such as a magnetic disk or optical disk, is provided and coupled to bus for storing information and instructions.

The computer system may be coupled via bus to a display, such as an LCD, for displaying information to a computer user. An input device, including alphanumeric and other keys, may be coupled to bus for communicating information and command selections to processor. Another type of user input device is cursor control, such as a mouse, a trackball, touchscreen (e.g., on mobile phones) or cursor direction keys for communicating direction information and command selections to processor and for controlling cursor movement on display. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allows the device to specify positions in a plane.

The computer system may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computer system causes or programs computer system to provide specialized features. According to one embodiment, the techniques herein are performed by the computer system in response to the processor executing one or more sequences of one or more instructions contained in main memory. Such instructions may be read into main memory from another storage medium, such as storage device. Execution of the sequences of instructions contained in main memory causes the processor to perform the process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions.

The term storage media as used herein refers to any non-transitory media that stores data and/or instructions that cause a machine to operation in a specific fashion. Such storage media may comprise non-volatile media and/or volatile media. Non-volatile media includes, for example, optical or magnetic disks, such as storage device. Volatile media includes dynamic memory, such as main memory. Common forms of storage media include, for example, a floppy disk, a flexible disk, hard disk, solid state drive, magnetic tape, or any other magnetic data storage medium, a CD-ROM, any other optical data storage medium, any physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, NVRAM, any other memory chip or cartridge.

Storage media is distinct from but may be used in conjunction with transmission media. Transmission media participates in transferring information between storage media. For example, transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise bus. Transmission media can also take the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications.

Various forms of media may be involved in carrying one or more sequences of one or more instructions to the processor for execution. For example, the instructions may initially be carried on a magnetic disk or solid state drive of a remote computer. A bus carries the data to main memory, from which processor retrieves and executes the instructions. The instructions received by main memory may optionally be stored on storage device either before or after execution by the processor.

The computer system also includes a communication interface coupled to bus. The communication interface provides a two-way data communication coupling to a network link that is connected to a local network. For example, the communication interface may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.

Network link typically provides data communication through one or more networks to other data devices. For instance, network link may provide a connection through local network to a host computer or to data equipment operated by an Internet Service Provider (ISP). ISP in turn provides data communication services through the worldwide packet data communication network now commonly referred to as the “Internet.” Local network and Internet both use electrical, electromagnetic or optical signals that carry digital data streams. The signals through the various networks and the signals on network link and through the communication interface, which carry the digital data to and from the computer system, are example forms of transmission media.

The computer system can send messages and receive data, including program code, through the network(s), network link and the communication interface. In the Internet example, a server might transmit a requested code for an application program through Internet, ISP, local network and the communication interface.

The received code may be executed by the processor as it is received, and/or stored in storage device, or other non-volatile storage for later execution.

It should be understood that variations, clarifications, or modifications are contemplated. Applications of the technology to other fields are also contemplated.

Exemplary systems, devices, components, and methods are described for illustrative purposes. Further, since numerous modifications and changes will readily be apparent to those having ordinary skill in the art, it is not desired to limit the invention to the exact constructions as demonstrated in this disclosure. Accordingly, all suitable modifications and equivalents may be resorted to falling within the scope of the invention.

Thus, for example, any sequence(s) and/or temporal order of steps of various processes or methods that are described herein are illustrative and should not be interpreted as being restrictive. Accordingly, it should be understood that although steps of various processes or methods or connections or sequence of operations may be shown and described as being in a sequence or temporal order, but they are not necessarily limited to being carried out in any particular sequence or order. For example, the steps in such processes or methods generally may be carried out in various different sequences and orders, while still falling within the scope of the present invention. Moreover, in some discussions, it would be evident to those of ordinary skill in the art that a subsequent action, process, or feature is in response to an earlier action, process, or feature.

It is also implicit and understood that the applications or systems illustratively described herein provide computer-implemented functionality that automatically performs a process or process steps unless the description explicitly describes user intervention or manual operation.

It is understood from the above description that the functionality and features of the systems, devices, components, or methods of embodiments of the present invention include generating and sending signals to accomplish the actions.

It should be understood that claims that include fewer limitations, broader claims, such as claims without requiring a certain feature or process step in the appended claim or in the specification, clarifications to the claim elements, different combinations, and alternative implementations based on the specification, or different uses, are also contemplated by the embodiments of the present invention.

It should be understood that combinations of described features or steps are contemplated even if they are not described directly together or not in the same context.

The terms or words that are used herein are directed to those of ordinary skill in the art in this field of technology and the meaning of those terms or words will be understood from terminology used in that field or can be reasonably interpreted based on the plain English meaning of the words in conjunction with knowledge in this field of technology. This includes an understanding of implicit features that for example may involve multiple possibilities, but to a person of ordinary skill in the art a reasonable or primary understanding or meaning is understood.

It should be understood that the above-described examples are merely illustrative of some of the many specific examples that represent the principles described herein. Clearly, those skilled in the art can readily devise numerous other arrangements without departing from the scope of the present invention. 

What is claimed is:
 1. A system for developing software comprising: at least one processor; and at least one memory operatively coupled to the at least one processor, the at least one processor configured to acquire computer readable instructions stored in the at least one memory and execute the instructions comprising instructions to cause the system to: provide a graphical user interface on a display of a client device, the graphical user interface displaying a plurality of features from a library of user-selectable features for a custom software application and implement simulations of a plurality of the features available for demonstration through the graphical user interface; store blocks of source code for each feature in a source code repository, wherein the blocks are adapted to provide an actual application when compiled by developers; receive from the client device, by a server running a software building component of a software development application, one or more selected features for the software application; automatically integrate, by the software building component, the one or more selected features that generate an integrated feature set based on attributes of each of the selected features and an inter-feature rules set, wherein the system sends a query to a graph database implemented using nodes and edges and storing a history of projects and controlling connections between features using the graph database, and generate on the graphical user interface an interactive visualization of a navigable prototype of the software application based on the integrated feature set.
 2. The system of claim 1, wherein the inter-features rules set define relationships or associations between features of the library of features.
 3. The system of claim 2, wherein the system is configured to include an embedding pipeline that responds to queries.
 4. The system of claim 1, wherein the instructions further comprise instructions to cause the system to automatically identify and add a new feature from the library of features to the selected features based on the inter-features rules set.
 5. The system of claim 1, wherein the attributes of a feature comprise a first set of attributes configured to regulate how the feature may be called, and a second set of attributes configured to regulate which features the feature may call.
 6. The system of claim 5, wherein the feature comprises an interactive region configured to host an interactive element, the interactive element being configured to link to another feature and call that feature when the interactive element is actuated.
 7. The system of claim 1, wherein the instructions further comprise instructions to cause the system to generate a screen flow view of the integrated features set, the screen flow view comprising the features of the integrated set interlinked by connectors that represent the relationships between the features.
 8. The system of claim 7, wherein both the features of the integrated set and the connectors between can be edited on the screen flow view.
 9. The system of claim 8, wherein the graph database is used to control actions in the system.
 10. The system of claim 1, wherein the instructions further comprise instructions to cause the system to generate source code for the software application based on the integrated feature set and using the blocks of source code.
 11. The system of claim 1, wherein the instructions further comprise instructions to cause the system to provide the user with the opportunity to select a template from one or more templates, wherein each template comprises a set of predetermined interconnected features, and subsequently provide the user via the graphical user interface the opportunity to select to add features to the template, and in response, the system is configured to automatically interconnect the selected added features with the set of predetermined interconnected features by using the inter-features rule set, which provides an interactive prototype within the graphical user interface.
 12. A computer-implemented method of a developing software comprising: providing a graphical user interface on a display of a client device, the graphical user interface displaying a plurality of features from a library of user-selectable features for a custom software application; implementing simulations of a plurality of the features available for demonstration through the graphical user interface; receiving from the client device, by a server running a software building component of a software development application, one or more selected features for the software application; automatically integrating, by the software building component, the one or more selected features that generate an integrated feature set based on attributes of each of the selected features and an inter-feature rules set, wherein the system sends a query to a graph database implemented using nodes and edges and storing a history of projects and controlling connections between features using the graph database; and generating on the graphical user interface an interactive visualization of a navigable prototype of the software application based on the integrated feature set.
 13. The method of claim 12, wherein the inter-features rules set define relationships or associations between features of the library of features.
 14. The method of claim 12, wherein the method including an embedding pipeline that responds to queries.
 15. The method of claim 14, further comprising automatically identifying and adding a new feature from the library of features to the selected features based on a recommendation from the graph database.
 16. The method of claim 12, wherein the attributes of a feature comprise a first set of attributes configured to regulate how the feature may be called, and a second set of attributes configured to regulate which features the feature may call.
 17. The method of claim 16, wherein the feature comprises an interactive region configured to host an interactive element, the interactive element being configured to link to another feature and call that feature when the interactive element is actuated.
 18. The method of claim 12, further comprising generating a screen flow view of the integrated features set, the screen flow view comprising the features of the integrated set interlinked by connectors that represent the relationships between the features.
 19. The method of claim 18, wherein both the features of the integrated set and the connectors between can be edited on the screen flow view.
 20. The method of claim 13, wherein one or more rules of the inter-features rules set are updated based on a history of selection of features for the software application. 